System and method for communicating between a communications management system using arinc 429 protocol and an internet protocol radio

ABSTRACT

An apparatus is provided. The apparatus comprises a processing system comprising: an ARINC 429 converter system; an Internet protocol (IP) suite; and an Ethernet driver; wherein the processing system is configured to be coupled to a communications management system and at least one IP radio; wherein the processing system converts data, from the communications management system, from an ARINC 429 protocol into a transport layer protocol, an IP and a Ethernet protocol; and wherein the processing system converts data, from the IP radio, from the Ethernet protocol, IP, and transport layer protocol to the ARINC 429 protocol.

BACKGROUND

A communications management system (CMS) enables data and messagingtransfers between an aircraft and ground based systems through one ormore subnetworks. Communications management systems may also be known ascommunications management units.

Conventional subnetworks commonly used to exchange data, such asmessages, include VHF, HF and satellite communications (SATCOM)communications aircraft communications addressing and reporting system(ACARS) networks. These subnetworks have limited bandwidth, and thusdata throughput, capabilities. However there is a demand for increasedbandwidth to facilitate increased throughput between aircraft and theground stations. Broadband subnetworks that have increased bandwidthinclude AeroMACS, broadband SATCOM, and L-band terrestrial networks.These subnetworks utilize standard Internet Protocol (IP).

Aircraft radios that communicate through such IP enabled subnetworks arereferred to as IP radios. IP radios utilize Ethernet link layer protocol(Ethernet protocol) communications to interface with other systems.Currently, CMSs on aircraft do not have the capability to interface withother systems, such as IP radios, using the Ethernet protocol.Therefore, there is a need to facilitate CMSs to communicate with IPradios.

SUMMARY

The embodiments of the present invention provide methods and systems forfacilitating a communications management system to communicate withInternet protocol (IP) radios, and will be understood by reading andstudying the following specification.

An apparatus is provided. The apparatus comprises a processing systemcomprising: an ARINC 429 converter system; an Internet protocol (IP)suite; and an Ethernet driver; wherein the processing system isconfigured to be coupled to a communications management system and atleast one IP radio; wherein the processing system converts data, fromthe communications management system, from an ARINC 429 protocol into atransport layer protocol, an IP and a Ethernet protocol; and wherein theprocessing system converts data, from the IP radio, from the Ethernetprotocol, IP, and transport layer protocol to the ARINC 429 protocol.

DRAWINGS

Understanding that the drawings depict only exemplary embodiments andare not therefore to be considered limiting in scope, the exemplaryembodiments will be described with additional specificity and detailthrough the use of the accompanying drawings, in which:

FIG. 1 illustrates one embodiment of an aircraft communicating with anoperations center, where the aircraft includes a communications systemincluding a protocol translator system;

FIG. 2 illustrates one embodiment of a communications system including aprotocol translator system;

FIG. 3 illustrates one embodiment of a communications management systemconfigured to be coupled to a protocol translator system;

FIG. 4 illustrates one embodiment of a protocol translator system;

FIG. 5 illustrates one embodiment of a method of converting data from anARINC 429 protocol received from a communications management system toan Ethernet protocol;

FIG. 6 illustrates one embodiment of a method of converting data in theEthernet protocol to the ARINC 429 protocol, and transmitting the datato a communications management system; and

FIG. 7 illustrates one embodiment of a data structure for a link dataunit comprised of data words.

In accordance with common practice, the various described features arenot drawn to scale but are drawn to emphasize specific features relevantto the exemplary embodiments.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings that form a part hereof, and in which is shown byway of specific illustrative embodiments in which the invention may bepracticed. These embodiments are described in sufficient detail toenable those skilled in the art to practice the invention, and it is tobe understood that other embodiments may be utilized and that logical,mechanical, and electrical changes may be made without departing fromthe scope of the present invention. The following detailed descriptionis, therefore, not to be taken in a limiting sense.

For pedagogical purposes, a vehicle may be described hereinafter as anaircraft. However, it is understood that the teachings herein areapplicable to other types of vehicles including without limitation otheraircraft, space craft, water borne vehicles (e.g. ships), submersibles,automobiles, buses, trains, and any other type of vehicle.

A protocol translator system, which is inserted between a communicationsmanagement system (CMS) and an IP radio, may be used to overcome theabove referenced problem. The protocol translator system facilitates anexternal addition of an Ethernet protocol interface to a CMS.

FIG. 1 illustrates one embodiment of an aircraft 102 communicating withan operations center 106, where the aircraft 102 includes acommunications system 100 including a protocol translator system. Theoperations center 106 may be an airline operations center, an operationscenter operated by a third-party service provider on behalf of one ormore airlines, an air traffic control center, or another type ofoperations center.

In one embodiment, the aircraft 102 communicates directly with theoperations center 106. In another embodiment, the aircraft 102communicates through a satellite with the operations center 106. In afurther embodiment, an intermediate communications system may couple thesatellite 104 and/or the aircraft 102 to the operations center 106.

Data, e.g. data messages, communicated from the aircraft 102 (e.g. fromthe CMS) to the operations center 106 shall be deemed downlink data.Data communicated from the operations center 106 to the aircraft 102(e.g. to the CMS) shall be deemed uplink data.

FIG. 2 illustrates one embodiment of a communications system 200including a protocol translator system (PTS) 204. The PTS 204 isconfigured to modify protocols of the downlink data and the uplink data,such as aircraft communications addressing and reporting system (ACARS)or aeronautical telecommunication (ATN) protocol messages. The PTS 204is coupled to the CMS 202 through an ARINC 429 communications link 219.The PTS 204 is coupled to one or more IP radios (IP radio(s)) 206through an Ethernet communications link 216. ARINC is derived fromAeronautical Radio, Incorporated. In another embodiment, the IP radio(s)206 comprise one or more radios configured to facilitate communicationswith the AeroMACS, the broadband SATCOM, and/or the L-band terrestrialsub-networks. In a further embodiment, the CMS 202 is coupled to one ormore of: at least one satellite data radio (SDR(s)) 208, at least one ahigh frequency data radio (HFDR(s)) 210, and at least one VHF data radio(VDR(s)) 212. SDR(s) 208 may also be known as SATCOM Data Unit(s)(SDU(s)).

In one embodiment, the PTS 204 may be part of another component, forexample a display controller such as a touch screen controller, e.g.which may include a touch screen display which replaces a multi-functioncontrol display unit (MCDU). Although illustrated in FIG. 2 as beingpart of the communications system, the display controller (shown as thePTS 204) and the display may not be part of the communications system200. To the extent not included already in the display controller, thedisplay controller, for example, would have to have added to it thecomponents illustrated in FIG. 3.

In one embodiment, the PTS 204 includes an Ethernet port, e.g. a Quadraxconnector, into which an Ethernet cable, that comprises the Ethernetlink 216, is inserted. It is beneficial to incorporate the PTS 204 intoan existing component such as the display controller because suchdisplay controller may already include such an Ethernet port, andpossibly also a processing system which can be used by components of theprocessing system, e.g. that are subsequently described.

FIG. 3 illustrates one embodiment of a communications management system302 configured to be coupled to the protocol translator system 204. TheCMS 302 comprises a first processing system 320 that includes a router322 configured to route data, such as messages, between radios (IPradio(s) 206, and possibly SDR(s) 208, HFDR(s) 210, VDR(s) 212, and/orother non-IP radio(s)), and the CMS 302 and/or external systems. Theradios are coupled to the CMS 302 through an ARINC 429 data bus 326. TheARINC 429 communications link 219 is coupled to the ARINC 429 data bus326. In another embodiment, the router 322 includes an IP router 322Aand at least one non-IP router (non-IP router(s)) 322B whichrespectively route messages to the IP radio(s) 206 and non-IP radios(e.g. SDR(s) 208, HFDR(s) 210, and/or VDR(s) 212). The data, e.g.messages, are generated by applications in external systems coupled tothe CMS 302 and/or by one or more messaging applications (messagingapplication(s)) 324 in the CMS 302. In a further embodiment, suchexternal systems include a flight management system (FMS) 328A and/or acentral maintenance computer (CMC) 328B. In yet another embodiment, theexternal systems include cabin terminal(s), an electronic flight bag,and/or aircraft condition monitoring systems.

In one embodiment, the first processing system 320 is a state machine,e.g. a combination of one or more processor(s), memor(ies), fieldprogrammable gate arrays, and/or application specific integratedcircuits (ASICs). The processor(s) may be central processing unit(s)and/or digital signal processing unit(s). The memor(ies) may be randomaccess memor(ies), read only memor(ies), flash memor(ies), and/ormagnetic memorie(s). In one embodiment, the router 322 and the messagingapplication(s) 324 are software stored, e.g. in the memor(ies), andexecuted by the processing system.

FIG. 4 illustrates one embodiment of the PTS 404. The PTS 404 converts:

(a) downlink data, such as ACARS and/or ATN messages, from the CMS 202from the ARINC 429 protocol into a transport layer protocol, the IP, andan Ethernet protocol; and

(b) uplink data, such as ACARS and/or ATN messages, from the IP radio(s)206 from the Ethernet protocol, the IP, and the transport layer protocolinto the ARINC 429 protocol.

In one embodiment, as will be subsequently illustrated, a bit-orientedfile transfer protocol of ARINC 429 is used where data is split intoLink Data Units (LDUs) each of which contains multiple ARINC 429 words(multiple words).

In the illustrated embodiment, the PTS 404 includes a processing system430. In another embodiment, the processor system 430 includes an ARINC429 converter system 430A, an Internet protocol suit (IPS) 430C, and anEthernet driver system 430D. In a further embodiment, the PTS 404includes a security management system 430B. In yet another embodimentthe PTS 404 includes an address lookup database 430E.

For the downlink data in the ARINC 429 protocol that is to be convertedto the transport layer protocol, the IP, and the Ethernet protocol, theARINC 429 converter system 430A extracts payload data from words(between the header words and the end of transmission word) of each LDUcomprising the downlink data, e.g. a message. In one embodiment, theARINC 429 converter system 430A and/or the IPS 430C combines the payloaddata from one or more LDUs to form a total data payload, e.g.corresponding to a message. In another embodiment, security data isappended to the total data payload. In a further embodiment, the totaldata payload (and security data—if used) is segmented, e.g. by the IPS430C, into data payloads; subsequently transport layer segments, IPdatagrams (each encapsulating a transport layer segment), and finallyEthernet frames (each encapsulating a IP datagram) are created, e.g. bythe IPS 430C and/or Ethernet driver system 430D, with the data payloads.

In one embodiment, for the uplink data in the Ethernet protocol, the IP,and the transport layer protocol that is being converted to the ARINC429 protocol, the IPS 430C extracts data payloads from each transportlayer segment. In one embodiment, the ARINC 429 converter system 430Aand/or the IPS 430C combines the data payloads from one or moretransport layer segments to form a total data payload, e.g.corresponding to a message, and the security data (if used). In anotherembodiment, the total data payload (and security data—if used) issegmented, e.g. by the ARINC 429 protocol converter system 430A, intopayload data; subsequently LDU(s) are created, e.g. by the ARINC 429protocol converter system 430A.

In one embodiment, the IPS 430C extracts only IP packets and/ortransport layer segments from Ethernet frames. In this embodiment, theextracted IP packets or transport layer segments may be combined intosets, and converted individually or as sets into ARINC 429 protocol bythe ARINC 429 converter system 430A, and communicatively coupled to theCMS 302. One or more portions of an IPS are located in the CMS 302, e.g.in the first processing system 320, and facilitate (a) extraction oftransport layer segments from IP packets and/or extraction of datapayloads from transport layer segments, and (b) combination of datapayloads to create a total data payload.

For the purposes of clarity, the data, e.g. corresponding to subjectmatter of a message but excluding source, destination, error correction,and other administrative information shall be referred to as a datapayload for transport layer segments, IP packets and Ethernet frames,and payload data for LDUs. Such data payload shall be the data of eachtransport layer segment. Such payload data shall be the data of eachLDU. The combination of either of the data payload or payload data shallbe referred to as the total data payload.

In one embodiment, for the downlink data in the ARINC 429 protocol thatis being converted to the transport layer protocol, the IP, and theEthernet protocol, the IPS 430C creates transport layer segments usingone of two transport layer protocols: user datagram protocol (UDP) ortransmission control protocol (TCP). Each transport layer segment has aheader (corresponding to the transport layer protocol utilized) appendedto the data payload. The amount of data included in each segment isselected by the designer of the system or defined by a standard.

In one embodiment, data is formed into transport layer segments and/orIPs by a portion of the IPS located in the CMS 302, e.g. by the firstprocessing system 320. Such data is communicatively coupled from the CMS302 to the protocol translator system 404. The portion of the IPS in theprotocol translator system 404 extracts transport layer segments and/orIPs from downlink data in the ARINC 429 protocol. In this embodiment,the extracted transport layer segments or IPs are converted respectivelyto IPs and Ethernet frames, or Ethernet frames by the portion of the IPS430C in the protocol translator system 404, and communicatively coupledto the IP radio(s) 206. In the CMS 302, the data payloads of eachtransport layer segment are extracted and combined in the portion of theIPS in the protocol translator system 404. For example, the portion ofthe IPS in the protocol translator system 404 is located in the firstprocessing system.

The IPS 430C then adds an IP header to each transport layer segment toform an IP packet. Finally, the IPS 430C and/or the Ethernet driversystem 430D adds an Ethernet header and trailer to each IP packet toform an Ethernet frame.

In one embodiment, the security data includes a digital signature and/orcyclic redundancy check (CRC) value. If security data is extracted,then, the security data is analyzed as described below.

The Ethernet driver system 430D communicates with the IPS 430C throughan application program interface and facilitates obtaining informationfrom hardware, e.g. of the IP radio(s) 206 and the PTS 404, about sourceand destination media access controller address(es). The Ethernet driversystem 430D also facilitates transmitting and receiving the Ethernetframes through the hardware. In one embodiment, such hardware includesmedia access controller(s).

The security management system 430B verifies, and/or adds, a layer ofsecurity respectively in and/or to the data payload. The securitymanagement system 430B is intended to prevent malicious communicationsfrom being surreptitiously received and processed by the communicationssystem 200. This technique is illustrated in U.S. patent applicationSer. No. 15/498,415 filed on Apr. 26, 2017 and entitled “Systems andMethods for Secure Communications Over Broadband Datalinks,” which ishereby incorporated by reference in its entirety. To the extent adigital signature and/or a CRC value are appended to the data, thesecurity management system 430B analyzes and verifies the digitalsignature and/or the CRC value to ensure that the received data had notbeen maliciously manipulated or sent by an unauthorized source, e.g.pretending to be a legitimate operations center. In one embodiment, theCRC value is calculated and verified based upon the remainder of apolynomial division of the data. In another embodiment, the digitalsignature is created using public key infrastructure technology, and,e.g. a private key associated with the source of the data payload, forexample an operations center 106. In a further embodiment, the securitymanagement system 430B can also append the digital signature and/or theCRC value to downlink total data payload, e.g. before segmentation tocreate transport layer segments. In yet another embodiment, the securitymanagement system 430B is located in the CMS 302, e.g. the firstprocessing system 322; therefore, the digital signature and/or CRC valuewould be appended to and/or extracted from data in CMS 302.

In one embodiment, the address lookup database 430E stores one or moreIP addresses and port numbers of the destinations, e.g. operationcenter(s), with which the IP radio(s) 206 communicate. In anotherembodiment, the address lookup database 430E includes an airlineidentifier and a corresponding destination IP address and port number,e.g. to be used to create the IP header. In a further embodiment, theaddress lookup database 430E includes a source IP address and port, e.g.for the IPS 430C to create the IP header. For data being sent from anairplane to a ground station that is an airline operations center (AOC),ARINC 429 protocol data will include an airline indicator stored in anLDU of the data being sent. In yet another embodiment, based upon suchairline indicator, for example extracted from by the ARINC 429 convertersystem 430A, the IPS 430C will obtains the destination IP address andport for the corresponding AOC from the address lookup database 430E,and inserts such destination IP address and port, and the source IPaddress and port into the IP header.

FIG. 5 illustrates one embodiment of a method of converting data fromARINC 429 protocol received from a communications management system tothe Ethernet protocol 500. To the extent that the embodiment of themethod shown in FIG. 5 is described herein as being implemented in thesystems shown in FIGS. 1 through 4, it is to be understood that otherembodiments can be implemented in other ways. The blocks of the flowdiagrams have been arranged in a generally sequential manner for ease ofexplanation; however, it is to be understood that this arrangement ismerely exemplary, and it should be recognized that the processingassociated with the methods (and the blocks shown in the Figure) canoccur in a different order (for example, where at least some of theprocessing associated with the blocks is performed in parallel and/or inan event-driven manner).

In one embodiment, in block 540, route data, e.g. with the CMS 302 (forexample with the IP router 322A) to an IP radio through the PTS 204. Inblock 542, receive data in ARINC 429 protocol from a CMS 202, e.g. atthe PTS 204. The data may have originated in application(s) in the CMSor in other systems such as a flight management system or a centralmaintenance computer.

In one embodiment, in block 544, construct a total data payload 591,e.g. in the PTS 404 such as with the ARINC 429 protocol converter 430Aor the IPS 430C. Such total data payload 591 is formed by payload datafrom one or more LDUs of the received data in the ARINC 429 protocol.

In one embodiment, in block 546 generate and append security data to thetotal data payload 591, e.g. with the security management system 430B.In another embodiment, the security data comprises a CRC value and/or adigital signature.

In block 548, generate transport layer segments with each having atransport layer segment header (TCP) 547, e.g. using the IPS 430C (suchas the transport layer functionality of the IPS 430C). Each transportlayer segment includes all or a portion of the total data payload 541.In one embodiment, if security data has been generated it will beincluded in the last transport layer segment. Each transport layersegment header includes source and destination ports and a checksumvalue. The source and destination ports are endpoints to logicalconnections. The checksum, e.g. the sum of the payload data bytes, isused at the endpoint to verify that the data payload of the transportlayer segment was received without error. The TCP transport layersegment header also includes a sequence number to facilitate a recipientof the transport layer segments to reassemble the payload data 541 (andsecurity data if appended) in the correct order. TCP is used tosymbolize the transport layer segment header 547 for illustrativepurposes; however, the transport layer can utilize TCP or UDP, and thusthe transport layer segment header 547 can be a TCP or UDP header.

In block 550, generate and append an IP header 549, e.g. using the IPS430C (such as the IP functionality of the IPS 430), to each transportlayer segment. This forms an IP packet. The IP header includes thesource IP address and the destination IP address. It may also includetime-to-live data that limits the lifespan of that portion of payloaddata and/or security data contained in the IP packet.

In block 552, generate and append an Ethernet header 551A and anEthernet trailer 551B to the IP packet. This forms an Ethernet frame. Inone embodiment, the IPS 430C (such as the Ethernet functionality of theIPS 430C) and/or the Ethernet driver system 430D are used to perform thegeneration and appending function. The Ethernet header 551A includes thesource and destination media access controller addresses. The Ethernettrailer 551B includes a frame check sequence, which is a CRC value thatis used by the recipient of the Ethernet frame to detect any datacorruption within the frame arising during communications. In block 554,transmit the Ethernet frame, e.g. to an IP radio over the Ethernetcommunications link 216.

FIG. 6 illustrates one embodiment of a method of converting data in theEthernet protocol to ARINC 429 protocol, and transmitting the data to acommunications management system 600. To the extent that the embodimentof the method shown in FIG. 6 is described herein as being implementedin the systems shown in FIGS. 1-4, it is to be understood that otherembodiments can be implemented in other ways. The blocks of the flowdiagrams have been arranged in a generally sequential manner for ease ofexplanation; however, it is to be understood that this arrangement ismerely exemplary, and it should be recognized that the processingassociated with the methods (and the blocks shown in the Figure) canoccur in a different order (for example, where at least some of theprocessing associated with the blocks is performed in parallel and/or inan event-driven manner).

In block 660, receive data, e.g. from an IP radio 206 at the PTS 204, inEthernet frames. In one embodiment, proceed to block 667. Alternatively,in another embodiment, proceed to block 662.

In block 662, extract security data, i.e. the CRC value 643 and/or thedigital signature 645. In one embodiment, extract the security data fromthe last transport layer segment. If the security data is extracted,then, in block 664, verify the security data, e.g. to ensure theauthenticity of the data's source and/or that the data has not beenmaliciously altered. If the security data can not be verified, then, inblock 665, discard the corresponding total data payload 691.

In one embodiment, security data is verified by extracting andreassembling the data payloads 541 of each transport layer segment toform the total data payload 691, calculating a CRC value from the totaldata payload 691, and comparing the calculated CRC value to the CRCvalue in the security data; if they are the same the total data payload691 is verified as not having been altered. In another embodiment, thedigital signature is validated with public key infrastructure technologyusing a public key associated with the source; if the digital signaturevalidation is successful, then the authenticity of source of the totaldata payload 691 is verified. In a further embodiment, different sourcesof total data payload 691 (e.g. different operation centers 106) mayhave different private keys; in yet another embodiment, thecorresponding public keys associated with the different sources may beindexed by source (e.g. operations center) and thus stored in theaddress lookup database 430E.

If the security data is verified, then proceed to block 667. In oneembodiment, in block 667, extract the total data payload 691 if this wasnot already performed, e.g. in block 662. In one embodiment, extract thetotal data payload 691 by extracting and then reassembling the datapayloads 541 of each transport layer segment to form the total datapayload 691.

In block 670, generate data in the ARINC 429 protocol, e.g. with theARINC 429 converter system 430A. In one embodiment, generating the datain the ARINC 429 protocol comprises forming payload data, e.g. bysegmenting the total data payload 691. Then, LDU(s) are generated usingthe payload data, e.g. with the ARINC 429 converter system 430A.

FIG. 7 illustrates one embodiment of a data structure for a link dataunit 700 comprised of data words 700A-700N. Data words 700F, 700G, 700Nrespectively comprise portions of payload data 702A, 702B, 702N of theLDU 700. In one embodiment, data (such as a message) may comprise morethan one LDU 700. Returning to FIG. 6, in block 672 transmit data in theARINC 429 protocol to the communications management system 202.

Example Embodiments

Example 1 includes an apparatus, comprising: a processing systemcomprising: an ARINC 429 converter system; an Internet protocol (IP)suite; and an Ethernet driver; wherein the processing system isconfigured to be coupled to a communications management system and atleast one IP radio; wherein the processing system converts data, fromthe communications management system, from an ARINC 429 protocol into atransport layer protocol, an IP and a Ethernet protocol; and wherein theprocessing system converts data, from the at least one IP radio, fromthe Ethernet protocol, IP, and transport layer protocol to the ARINC 429protocol.

Example 2 includes the apparatus of Example 1, wherein the processingsystem further comprises a security management system; and wherein thesecurity management system analyzes security data appended to a totaldata payload received by the at least one IP radio.

Example 3 includes the apparatus of Example 2, wherein the security datacomprises at least one of a digital signature and a cyclic redundancycheck value.

Example 4 includes the apparatus of any of Examples 2-3, wherein thesecurity management system appends security data to a total data payloaddata received from the communications management system.

Example 5 includes the apparatus of any of Examples 1-4, wherein theprocessing system further comprises an address lookup databasecomprising at least one destination IP address.

Example 6 includes the apparatus of any of Examples 1-5, wherein theprocessing system is part of a display controller.

Example 7 includes the apparatus of any of Examples 1-6, furthercomprising the communications management system coupled to the protocoltranslator system; wherein the communications management system isconfigured to be coupled to at least one non-IP radio; wherein thecommunications management system comprises a first processing systemcomprising a router; and wherein the router routes data to and from theat least one IP radio.

Example 8 includes the apparatus of Example 7, wherein thecommunications management unit comprises a portion of the IP suite.

Example 9 includes a method, comprising: receiving data in an ARINC 429protocol from a communications management system; converting data in theARINC 429 protocol to an Ethernet protocol; and transmitting theconverted data to a radio.

Example 10 includes the method of Example 9, wherein converting data inthe ARINC 429 protocol to transport layer protocol, IP and the Ethernetprotocol, comprises: extracting payload data from each link data unit;and combining the payload data from each link data unit.

Example 11 includes the method of any of Examples 9-10, whereinconverting data in the ARINC 429 protocol to the transport layerprotocol, IP, and Ethernet protocol comprises: creating transport layersegments, wherein each segment has a transport layer segment header;adding an IP header to each transport layer segment to form IP packets;and adding an Ethernet header and an Ethernet trailer to each IP packetto form Ethernet frames.

Example 12 includes the method of any of Examples 9-11, furthercomprising: appending, to payload data of the data, security data.

Example 13 includes the method of Example 12, wherein appending securitydata comprises appending at least one of a cyclic redundancy check valueand a digital signature.

Example 14 includes a method, comprising: receiving data in an Ethernetprotocol, Internet protocol (IP), and transport layer protocol from anIP radio; converting the data in the Ethernet protocol, IP, andtransport layer protocol to the ARINC 429 protocol; and transmitting theconverted data to a communications management system.

Example 15 includes the method of Example 14, wherein converting thedata comprises: extracting a data payload from each transport layersegment; and combining the data payload.

Example 16 includes the method of any of Examples 14-15, whereinconverting data in the Ethernet protocol, IP, and transport layerprotocol to the ARINC 429 protocol comprises creating at least one linkdata unit (LDU), wherein each LDU is comprised of words.

Example 17 includes the method of any of Examples 14-16, furthercomprising: extracting, from security data; and verifying the securitydata.

Example 18 includes the method of Example 17, further comprisingdiscarding the total data payload if the security data can not beverified.

Example 19 includes the method of any of Examples 17-18, whereinextracting security data comprises extracting at least one of a cyclicredundancy check (CRC) value and a digital signature from a total datapayload.

Example 20 include the method of Example 14, wherein converting data inthe Ethernet protocol to the ARINC 429 protocol comprises convertingdata in the Ethernet protocol to an Internet protocol (IP) and atransport layer protocol.

1. An apparatus, comprising: a processing system comprising processingcircuitry coupled to memory circuitry; wherein the processing system isconfigured to be communicatively coupled to a communications managementsystem and at least one Internet protocol (IP) radio; wherein theprocessing system is configured to convert data, from the communicationsmanagement system, from an Aeronautical Radio Incorporated (ARINC) 429protocol into at least one of a transport layer protocol, an IP, and anEthernet protocol by: extracting payload data from each link data unit(LDU) of the data in the ARINC 429 protocol; forming a total datapayload by combining the payload data from each LDU; creating at leastone of: at least one transport layer segment each of which comprises atleast a portion of the total data payload, where each transport layersegment has a transport layer segment header; at least one IP packet bygenerating an IP packet header for each of the at least one transportlayer segment, and adding the IP packet header to the correspondingtransport layer segment; and at least one Ethernet frame by generatingan Ethernet header and an Ethernet trailer for each of the at least oneIP packet, and adding the Ethernet header and the Ethernet trailer torespectively the beginning and end of the corresponding IP packet; andwherein the processing system is configured to convert data, from the atleast one IP radio, from the Ethernet protocol to the ARINC 429 protocolby: extracting at least one of data payloads of each transport layersegment and datagrams of each IP packet; creating a total data payloadby combining one of the extracted data payloads and the extracteddatagrams; segmenting the total data payload into segmented payloaddata; and generating a link data unit (LDU) for each segmented payloaddata.
 2. The apparatus of claim 1, wherein the processing system furtheris further configured to analyze security data appended to a total datapayload received by the at least one IP radio.
 3. The apparatus of claim2, wherein the security data comprises at least one of a digitalsignature and a cyclic redundancy check value.
 4. The apparatus of claim2, wherein the processing system is further configured to appendsecurity data to a total data payload data received from thecommunications management system.
 5. The apparatus of claim 1, whereinthe processing system further comprises an address lookup databasecomprising at least one destination IP address.
 6. The apparatus ofclaim 1, wherein the processing system is part of a display controller.7. The apparatus of claim 1, further comprising the communicationsmanagement system coupled to the processing system; wherein thecommunications management system is configured to be coupled to at leastone non-IP radio; wherein the communications management system comprisesa first processing system comprising a router; and wherein the routerroutes data to and from the at least one IP radio.
 8. The apparatus ofclaim 7, wherein the communications management unit comprises a portionof an IP suite.
 9. A method, comprising: receiving data in anAeronautical Radio Incorporated (ARINC) 429 protocol from acommunications management system; converting data in the ARINC 429protocol to an Ethernet protocol by: extracting payload data from eachlink data unit (LDU) of the data in the ARINC 429 protocol; forming atotal data payload by combining the payload data from each LDU; creatingat least one of: at least one transport layer segment each of whichcomprises at least a portion of the total data payload, where eachtransport layer segment has a transport layer segment header; at leastone IP packet by generating an IP packet header for each of the at leastone transport layer segment, and adding the IP packet header to thecorresponding transport layer segment; and at least one Ethernet frameby generating an Ethernet header and an Ethernet trailer for each of theat least one IP packet, and adding the Ethernet header and the Ethernettrailer to respectively the beginning and end of the corresponding IPpacket; and transmitting the converted data to an IP radio. 10.(canceled)
 11. (canceled)
 12. The method of claim 9, further comprisingappending security data to the total data payload.
 13. The method ofclaim 9, wherein converting data in the ARINC 429 protocol to theEthernet protocol comprises converting data in the ARINC 429 protocol toa transport layer protocol and an Internet protocol (IP).
 14. A method,comprising: receiving data in an Ethernet protocol, Internet protocol(IP), and transport layer protocol from an IP radio; converting the datain the Ethernet protocol to the Aeronautical Radio Incorporated (ARINC429) protocol by: extracting at least one of data payloads of eachtransport layer segment and datagrams of each IP packet; creating atotal data payload by combining one of the extracted data payloads andthe extracted datagrams; segmenting the total data payload intosegmented payload data; and generating a link data unit (LDU) for eachsegmented payload data; and transmitting the converted data to acommunications management system.
 15. (canceled)
 16. The method of claim14, wherein each LDU is comprised of words.
 17. The method of claim 14,further comprising: extracting security data; and verifying the securitydata.
 18. The method of claim 17, further comprising discarding thetotal data payload if the security data can not be verified.
 19. Themethod of claim 17, wherein extracting security data comprisesextracting at least one of a cyclic redundancy check (CRC) value and adigital signature from a total data payload.
 20. The method of claim 14,wherein converting data in the Ethernet protocol to the ARINC 429protocol comprises converting data in the Ethernet protocol to anInternet protocol (IP) and a transport layer protocol.